hey dominik, went through this. content structure is solid - overview/design/operators/users is the right split. but the proto snippets in users.md don't match the actual proto. commitment_block_num, note_metadata, and FetchNotesRequest.limit don't exist in miden_note_transport.proto - only header and details. the block-context sections in design.md and users.md describe behavior the server doesn't have yet. these need to be regenerated from the real proto before merge.

not 100% sure on all of these yet but from a brief pass cross-referencing the source, seems like:

• --enable-otel and --otel-endpoint aren't actual CLI flags - telemetry looks like it's controlled by OTEL_ENABLED / OTEL_TRACES_ENDPOINT env vars instead
• make docker-build-node and make docker-run-node don't exist in the Makefile, only docker-node-up/down/restart
• Docker persistence might be broken - Compose sets DATABASE_URL but the binary doesn't read it, so it could be defaulting to :memory:

also not 100% confirmed but from what i can tell:

• "NTL does not deduplicate notes" looks wrong - there's a UNIQUE constraint on note id in the DB schema, so dupes would fail
• streaming cursor behavior seems different from what's documented here - server might be ignoring the client-provided cursor

i'll review the issues i raised above more deeply and fix them. will also update this PR to follow the ingestion path instead of a standalone docusaurus site - same pattern as miden-client and node. i'll restructure the content under docs/external/src/ and create a separate PR in the docs repo to wire up the ingestion. will push updates to this branch.